Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DM-43490: Put correct size to PixelGrid for PSF estimation #25

Merged
merged 10 commits into from
May 22, 2024

Conversation

arunkannawadi
Copy link
Member

No description provided.

@esheldon
Copy link
Contributor

Where do we stand on this PR?

@arunkannawadi
Copy link
Member Author

If we are willing to drop the problematic rotation angles from the tests, I can go ahead with this. The GalSim changes aren't in rubin-env so this will break the build as is.

@esheldon
Copy link
Contributor

what is the timescale for the new galsim getting into the rubin env?

@timj
Copy link
Member

timj commented May 14, 2024

rubin-env 9, see DM-43326 -- so you can add that ticket as a blocker to DM-43490.

@arunkannawadi
Copy link
Member Author

Already done linking the two tickets. I could drop the 45 degree angle (that one fails) and note a different ticket that gets trigggered after rubin-env 9 is out.

@arunkannawadi
Copy link
Member Author

Currently, two tickets are blocked, waiting specifically on galsim 2.5.2 to get into the environment.

@arunkannawadi
Copy link
Member Author

arunkannawadi commented May 14, 2024

I don't want Erin to rely on his fork longer than necessary. It would have already diverged from the main branch. I'll conditionally skip the test based on the galsim version available and mark the skipping for removal in a later ticket.

arunkannawadi and others added 9 commits May 17, 2024 15:47
Setting it to -1 messes up the static type checker(s). Setting it to -1.
leads to correct type interpretation.
with an option to rotate it by an arbitrary angle.

Co-authored-by: Erin Sheldon <[email protected]>
@arunkannawadi arunkannawadi marked this pull request as ready for review May 17, 2024 22:48
@arunkannawadi
Copy link
Member Author

The cutout size that are fed into Piff cannot be adjusted from this package. That happens upstream in pipe_tasks and changing the default value and additional checks happen there: lsst/pipe_tasks#933


wcs = make_wcs(angle_degrees=45)
self.exposure.setWcs(wcs)
self.checkPiffDeterminer(useCoordinates='sky', kernelSize=35)
Copy link
Member Author

@arunkannawadi arunkannawadi May 17, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@timj Strictly speaking, this would get merged without ever being run on our CI systems. Should I include it, or add a note to add this test case in a later ticket?

Copy link

@PFLeget PFLeget left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. I left one comment on it!

@@ -307,7 +358,7 @@ def checkPiffDeterminer(self, **kwargs):
chiLim = 7.0
else:
numAvail = len(psfCandidateList)
chiLim = 6.1
chiLim = 6.4
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this switched from 6.1 to 6.4?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@esheldon increased it to 6.5 and I found 6.4 was sufficient for tests to pass. Do you have an intuition as to why the increase was necessary with the rotations, Erin?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought it was probably just noise.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It could be. I don't think there was any first-principle motivation for chiLim = 6.1 in the first place, just a value chosen empirically.

Thresholds in pipelines_check repo have to be changed only after announcing/asking the entire Science Pipelines team, but these ones can be changed by a reasonable amount.

@arunkannawadi arunkannawadi merged commit 607f77f into main May 22, 2024
2 checks passed
@arunkannawadi arunkannawadi deleted the tickets/DM-43490 branch May 22, 2024 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants